Defibrillator/monitor system having a pod with leads capable of wirelessly communicating

ABSTRACT

A modular external defibrillator system in embodiments of the teachings may include one or more of the following features: a base containing a defibrillator to deliver a defibrillation shock to a patient, (b) one or more pods each connectable to a patient via patient lead cables to collect at least one patient vital sign, the pods operable at a distance from the base, (c) a wireless communications link between the base and a selected one of the two or more pods to carry the at least one vital sign from the selected pod to the base, the selection being based on which pod is associated with the base.

This application is a continuation of application Ser. No. 10/583,209filed Dec. 17, 2004, which claimed priority to International PCTApplication No. PCT/US2004/012421 titled “Defibrillator/Monitor SystemHaving a Pod with Leads Capable of Wirelessly Communicating” filed onApr. 22, 2004, and claimed the benefit of U.S. Provisional ApplicationSer. No. 60/530,151 titled “Defibrillator/Monitor System Having a Podwith Leads Capable of Wirelessly Communicating” filed on Dec. 17, 2003,all of which are hereby incorporated by reference in their entirety.

This disclosure is related to the following co-pending PCT applicationsentitled “DEFIBRILLATOR PATIENT MONITORING POD,” InternationalApplication No. PCT/US2004/042792, Attorney Docket Number 539.6000.10,filed Dec. 17, 2004, and “AN EXTERNAL DEFIBRILLATOR WITH POWER ANDBATTERY SHARING CAPABILITIES WITH A POD,” International Application No.PCT/US2004/042376, Attorney Docket Number 539.6000.11 filed Dec. 17,2004, hereby incorporated by reference in their entirety and which arenot admitted as prior art with respect to the present disclosure bytheir mention in this section.

TECHNICAL FIELD

The teachings relate to medical devices, and in particular, todefibrillation/monitor systems having a detachable pod with leads.

BACKGROUND

Each day thousands of Americans are victims of cardiac emergencies.Cardiac emergencies typically strike without warning, oftentimesstriking people with no history of heart disease. The most commoncardiac emergency is sudden cardiac arrest (“SCA”). It is estimated morethan 1000 people per day are victims of SCA in the United States alone.

SCA occurs when the heart stops pumping blood. Usually SCA is due toabnormal electrical activity in the heart, resulting in an abnormalrhythm (arrhythmia). One such abnormal rhythm, ventricular fibrillation(VF), is caused by abnormal and very fast electrical activity in theheart. During VF the heart cannot pump blood effectively. Because bloodmay no longer be pumping effectively during VF, the chances of survivingdecreases with time after the onset of the emergency. Brain damage canoccur after the brain is deprived of oxygen for four to six minutes.

Applying an electric shock to the patient's heart through the use of adefibrillator treats VF. The shock clears the heart of the abnormalelectrical activity (in a process called “defibrillation”) bydepolarizing a critical mass of myocardial cells to allow spontaneousorganized myocardial depolarization to resume.

Cardiac arrest is a life-threatening medical condition that may betreated with external defibrillation. External defibrillation includesapplying electrodes to the patient's chest and delivering an electricshock to the patient to depolarize the patient's heart and restorenormal sinus rhythm. The chance a patient's heart can be successfullydefibrillated increases significantly if a defibrillation pulse isapplied quickly.

In a scenario where a patient on a gurney is being transported throughnarrow doorways and down stairwells to an ambulance, or the situationwhere a patient is in an ambulance moving on a road at high speed withpatient cables and IV (intravenous) lines running between the patientand other equipment within the ambulance, if the monitoring/therapeuticdevice is large or the route to the ambulance is particularly difficult,the paramedic might elect to carry the device separately from the gurneyto prevent the device falling off the gurney or onto the patient.However, the paramedic is now restricted in his or her ability to detachthe device from the gurney due to the number and length of patientcables between the device and the patient. Similar restrictions occuronce the patient is loaded into a patient transport vehicle or when thepatient is transferred from the ambulance to the emergency department.The number of cables and their similarity in color or dissimilarity inlength can all contribute to delays in treating or transferring thepatient and can restrict the paramedic's mobility when treating thepatient in a confined space. Additionally, delays may be created withcables having become tangled, or even cut, from their previous uses.

The prior art has tried to solve this problem by providing a wirelessmodule that transmits data to a patient monitor, such as the MobiMedoffered for Sale by Ortivus.

However, this device does not include a defibrillator and does not havethe capability to provide any therapeutic functions such as pacing,defibrillation or synchronous cardioversion without attaching anothermonitor/defibrillator to the patient, which further increases thecomplexity and ambulance provider cost. Additionally, the Ortivuspatient module does not offer replaceable batteries so functionality isseverely limited if a reliable source of battery charging is notavailable, or if the transport time is excessively long. Additionally,the Ortivus device does not offer a display to allow visual monitoringof the waveforms or vital signs if the other module is out of range orobscured.

Another problem arises when hospital personnel want to charge thebatteries of the defibrillator/monitor, but don't want to have to placethe unit in a docking station in order to charge the batteries. Therealso arises the issue of patient confidentiality, such as recentlyraised by the Federal HIPAA (Health Insurance Portability andAccountability Act) regulations, when identical looking patient monitorsare accidentally swapped by operators.

Another problem may occur in a situation where two or more sets ofassociated wireless devices are used in the same general area. This typeof problem could occur in a number of different (medical or non-medical)applications. For example, medical device A is comprised of two parts, apatient data acquisition module (AA) and a display module (AD). The twoparts communicate with each other via one of many wireless methods.Medical device B is comprised of two similar parts patient dataacquisition module (BA) and display module (BD). In the event of a masscasualty incident, where medical personnel are attending to more thanone patient, two or more patients may be laying close to each other.Suppose patient X is being attended to by the operator of device A, anda different operator who is using device B is attending to patient Y.Patient X's vital signs are being acquired by acquisition module AA andtransmitted to display module AD. Patient Y's vital signs are beingacquired by acquisition module BA and transmitted to display module BD.A problem could arise when, in the state of confusion typically existingin a mass casualty incident, the two display modules become switched. Inthis case, the operator of display module AD could be viewing the vitalsigns transmitted from Patient X while attending to Patient Y. Thiscould result in inappropriate administration of drugs or other therapywith potentially serious consequences. The acquisition modules couldstill be associated to the appropriate display modules, and could stillbe functioning properly, but the operator could be viewing the wrongpatient's vital signs.

Other problems with wireless communications include the fact wirelesscommunications methods cannot be visually assessed by the operator priorto failure, such as a broken or damaged cable can. Wirelesscommunications may not be permitted in critical areas, such as anaircraft environment, in military use, or elsewhere. Some wirelesscommunications means have delays between sending a message and getting aresponse which are too long for therapeutic and other needs. There is arisk of the operator not being able to find a cable when, for instance,a critical therapy has to be administered where the wireless link cannotsupport it.

SUMMARY

A modular external defibrillator system in embodiments of the teachingsmay include one or more of the following features: (a) a base containinga defibrillator to deliver a defibrillation shock to a patient, (b) oneor more pods each connectable to a patient via patient lead cables tocollect at least one patient vital sign, the pods operable at a distancefrom the base, and (c) a wireless communications link between the baseand a selected one of the one or more pods to carry the at least onevital sign from the selected pod to the base, the selection being basedon which pod is associated with the base.

A modular external defibrillator system in embodiments of the teachingsmay include one or more of the following features: (a) a base containinga defibrillator module to deliver a defibrillation shock to a patient,(b) two or more pods each having a patient parameter module andconnectable to a patient via patient lead cables to collect at least onepatient vital sign, the pods operable at a distance from the base, and(c) wireless communications links between the base and the two or morepods to carry the at least one vital sign from each pod to the base, thebase having a monitor portion to display the at least one vital signreceived from a selected one of the two or more pods.

A method of associating components in a modular external defibrillatorsystem in embodiments of the teachings may include one or more of thefollowing steps: (a) providing a base containing a defibrillator todeliver a defibrillation shock to a patient, (b) selecting a patientparameter pod to associate with the base, the selected pod beingconnectable to a patient via patient lead cables to collect patientdata, the selected pod being operable separate from the base, (c)establishing a communications link between the base and the selected podto carry the patient data from the pod to the base, and (d) testing thecommunications link to determine if association is successful.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a pictorial representation of an external defibrillator havinga patient module pod with a defibrillator/monitor base in an embodimentof the present teachings;

FIG. 2 is an upper level pictorial representation of a patient modulepod in an embodiment of the present teachings;

FIG. 3 is an upper level pictorial representation of adefibrillator/monitor base in an embodiment of the present teachings;

FIG. 4 is a schematic view of a patient module pod in an embodiment ofthe present teachings;

FIG. 4A is a pictorial representation of a multiple patient module podstorage and attachment assembly in an embodiment of the presentteachings;

FIG. 5 is a schematic view of a defibrillator/monitor base in anembodiment of the present teachings;

FIG. 6 is a diagram of a patient module pod and a defibrillator/monitorbased interaction in an embodiment of the present teachings;

FIG. 7 is a block diagram of different size a patient module pods adefibrillator/monitor base, a base docking station, AC or DC powersupplies, and a personal computer interaction in an embodiment of thepresent teachings;

FIG. 8 is a block level diagram of an association system for a patientmodule pod and a defibrillator/monitor base in an embodiment of thepresent teachings;

FIG. 9 is a pictorial representation of a connector in an embodiment ofthe present teachings;

FIG. 10 is a pictorial representation of a mating assembly having atethered connector in an embodiment of the present teachings;

FIG. 11 is a flow diagram of association between a device and a base inan embodiment of the present teachings;

FIG. 12 is a flow diagram of patient monitoring pod identificationfunction in an embodiment of the present teachings;

FIG. 13 is a flow diagram of a patient monitoring pod location functionin an embodiment of the present teachings.

DETAILED DESCRIPTION

The following discussion is presented to enable a person skilled in theart to make and use the present teachings. Various modifications to theillustrated embodiments will be readily apparent to those skilled in theart, and the generic principles herein may be applied to otherembodiments and applications without departing from the presentteachings. Thus, the present teachings are not intended to be limited tothe embodiments shown, but are to be accorded the widest scopeconsistent with the principles and features disclosed herein. Thefollowing detailed description is to be read with reference to thefigures, in which like elements in different figures have like referencenumerals. The figures, which are not necessarily to scale, depictselected embodiments and are not intended to limit the scope of thepresent teachings. Skilled artisans will recognize the examples providedherein have many useful alternatives that fall within the scope of thepresent teachings.

With reference to FIG. 1, a pictorial representation of an externaldefibrillator having a patient module with a defibrillator/monitor in anembodiment of the present teachings is shown. External defibrillator 10is comprised of two components patient module (pod) 12 anddefibrillator/monitor (base) 14, which communicate patient data (e.g.,vital signs) and share common replaceable battery technology. Pod 12generally rests within base 14, generally in the back of base 14. Theoperator, during an emergency, has the option of carrying base 14 withpod 12 attached or simply carrying pod 12 to the emergency site. Sincepod 12 is smaller and lighter than base 14, generally it will be easierfor the operator to simply carry pod 12. By carrying pod 12, theoperator is free to carry more ALS equipment and not be slowed by theheavier and more awkward base 14.

Pod 12 connects to a patient via several leads in order to measure thepatient's vital signs. Pod 12 communicates the patient's vital signseither wirelessly or via an electrical connection to defibrillatormonitor 14. The patient data or vital signs collected may include 3, 4,and 5 lead ECG readings, 12 lead ECG readings, non-invasive bloodpressure (NIBP), pulse oximeter data, capnography data, invasive bloodpressure, body temperature, C0₂ levels, and additional patientmonitoring functions. Additionally, pod 12 may include a small display82 (FIG. 4) replicating some or all of the information such aswaveforms, numerical data, and vital signs being transmitted to base 14.The patient data or vital signs may be collected with a multitude ofleads 11 such as an ECG lead 19, a non-invasive blood pressure lead 8,and pulse oximeter lead 6, extending from patient lead cable port 9 thatmay include many inputs if multiple lead cables are used.

Base 14 includes a therapy module 56 (FIG. 3) and therapy cables.Therapy module 56 has the capability to provide therapeutic functionssuch as pacing, defibrillation, or synchronous cardioversion withoutattaching another monitor/defibrillator to the patient. The therapycables typically include patient paddles or electrodes that attachbetween the patient and base 14 in order to deliver the therapy to thepatient. Since pod 12 connects to the patient and transmits vital signsto base 14, then base 14 need not also have patient monitoring cables.Accordingly, paramedic mobility and ease of use are greatly increased.Therapy module 56 in base 14 may be configurable in either an ALS modeor an AED mode. The A LS mode includes a multi-parameter monitoringcapability and all of the defibrillator therapy delivery capability.Additionally base unit 14 may be just an AED.

With reference to FIG. 2, an upper level pictorial representation of apatient module in an embodiment of the present teachings is shown.Generally, pod 12 uses replaceable or rechargeable batteries 16 forpower and comprises any combination of the following features: 3, 4, and5 lead ECG inputs 18, 12 lead ECG inputs 20, non-invasive blood pressure(NIBP) input 22, pulse oximeter input 24, capnography input (not shown),invasive blood pressure input 26, temperature input 28, CO₂ input 30,additional patient monitoring functions, transceiver 32 to transmit anyor all real time patient data to base 14. Transceiver 32 can be awireless BlueTooth module commercially available from TDK, however,transceiver 32 can be any transceiver such as WiFi (802.11), WirelessWAN(CDMA, GSM, GPRS, UTMS, etc.), or a wired Fire-Wire (IEEE 1394)without departing from the spirit of the present teachings.Additionally, pod 12 may include a small display 82 (FIG. 4) replicatingsome or all of the information such as waveforms, numerical data, andvital signs being transmitted to base 14. Additionally, pod 12 includessome means by which it can be attached and secured to base 14 for thepurpose of carrying base 14 to an emergency scene as is discussed in PCTApplication Serial No. US04/12421. Additionally, pod 12 may have afeature allowing it to be easily secured to a gurney or hospital bed.

With reference to FIG. 3, an upper level pictorial representation of adefibrillator/monitor in an embodiment of the present teachings isshown. Base 14 uses a replaceable or rechargeable battery 50 for power.Batteries 16 and 50 are generally similar in battery chemistry,electrical, and mechanical features to permit the interchangeabilitybetween batteries 16 and 50. Batteries 16 and 50 can be a LiIon batteryproviding 16 volts and 3.8 amps, however, most any type of battery canbe used without departing from the spirit of the invention.Additionally, base 14 comprises a display 52 sufficient to show currentand historical patient data, a transceiver (similar to transceiver 32[not shown]) to send acquired patient data onto a receiving station orthird party data receiver, a module 56 to synchronize shocks and pacingpulses to the patient's intrinsic rhythm from data acquired by a pod 12,an error checking and de-multiplexing module 54 receiving and processingdata received from pod 12, and a data interpretation module 58 whichanalyzes data acquired by pod 12 and makes certain interpretivestatements on the patient's cardiac or respiratory condition, displaysvital sign trends, and provides additional functions found in ALSmonitoring products.

With reference to FIG. 4, system controller module 66 controlsinteraction of all the pod's modules through data bus 64 and interactionwith base 14 through a wired connection, such as tethered cable 46 orwireless (e.g., IrDA, RF, etc.) communication link 72 which would betransmitted by transceiver 32 incorporated into system controller 66 aspart of an interconnect module. System controller module 66 h as theability to encrypt data communicated over the wireless links to meetHIPAA requirements for the protection of patient data. There can be asingle encryption key for all bases and pods. However, it iscontemplated there could be a user defined encryption key that can beset at the base by an operator. Patient parameter module 68 monitorsfunctions such as invasive blood pressure, patient's temperature, andinputs from the pod leads. Module 68 further collects inputs from EtCO₂module 74, NIBP module 76, and SpO₂ module 78 through OEM module 80.Patient parameter module 68 takes all of these inputs and processes themfor display and can route only a limited number of inputs to small LCDdisplay module 82 through operator interface module 70. PatientParameter Module 68 also has the ability to perform interpretation ofclinical data and can make certain interpretive statements about thepatient's condition (e.g., cardiac or respiratory health).

Power module 62 provides on/off control to the pod, utilizing theremovable battery 60 as the power source. Additional power managementoptions are disclosed in PCT application titled “AN EXTERNALDEFIBRILLATOR WITH POWER AND BATTERY SHARING CAPABILITIES WITH A POD,”International Application No. PCT/US2004/042376, Attorney Docket Number539.6000.11 filed Dec. 17, 2004, hereby incorporated by reference intheir entirety.

Operator Interface module 70 allows the operator to primarily interactwith pod 12; however, it is contemplated that operator could use themodule 70 to interact with base 14 as well.

With reference to FIG. 4A, a pictorial representation of a multiplepatient module storage and attachment assembly in an embodiment of thepresent invention is shown. Pods can come in different sizes generallyrepresenting the capability of the pod. For example, smaller pod 574′would provide only the basic features for an external defibrillator,while medium pod 574 would provide several additional features. In thepresent embodiment, pods 574 and 574′ can be docked together in mountingrecess or slot 572 contemporaneously. In one embodiment, pod 574 couldbe latched within mounting slot 572 communicating with base 571 throughconnector 573. Similarly, pod 574′ can be placed within mounting slot572 contemporaneously with pod 574 and latched in a communicatingrelationship with base 571 through connector 573′. In anotherembodiment, pods 574 and 574′ could be placed within mounting slot 572without the need for two base-to-pod connectors 573. Pod 574 and 574′latch together and communicate through connectors 570. Then both pods574 and 574′ are placed within mounting slot 572 and latched in acommunicating relationship with base 571 through connector 573. Thisembodiment not only limits the amount of connectors needed on base 571,but also allows the user to choose the amount of functions the pod canperform. For example, if the user simply needed to perform an ECG, thenthe user could choose to carry small pod 574′. However, if the emergencysituation required additional functions such as monitoring bloodpressure in a non-invasive method or a pulse oximeter, then the userwould choose to carry medium pod 574′. In addition, if the emergencysituation required all of the available pod functions, then pod 574′could be latched together with pod 574 to provide a large pod having allnecessary functions. It is also further contemplated connectors 573,573′, and 570 could be most any type of connector such as a USB port, anAC power connector, an RS-232 connector or any other type of connectorknown to those skilled in the art without departing from the spirit ofthe invention.

With reference to FIGS. 9 and 10, a pictorial representation of a matingassembly having a tethered connector in an embodiment of the presentteachings is shown. In this embodiment, a pod similar to 12 rests withinslot 40 and connects to base-to-pod connector 42, which allows base 14and a pod to communicate with each other. Base-to-pod connector 42 restsfreely within connector cavity 44, which allows connector cable 46 toretractably exit and enter base 14 as shown in FIGS. 9 and 10. Tetheredcable 46 allows a pod to mate with and rest within base 14 or mate withbase 14 when not docked within slot 40. It is sometimes helpful thatbase 14 communicate with a pod through tethered cable 46 sincecommunications through a direct connection is generally faster. This isthe case in the present embodiment as base 14 is equipped with a highspeed bus, such as a USB bus, which provides quick communication ofinformation between a pod and base 14. Base 14 is also able toautomatically detect when tethered cable 46 is plugged in so directcommunications can be established immediately. A direct communicationbetween a pod and base 14 can be established. This automaticestablishment of direct communication between a pod and base 14 includeswhen a pod is docked within base 14 and a connection is made between apod and base 14 through connector 42.

Generally base 14 and a pod communicate wirelessly to assist inpreventing the tangling of cables, which can occur between a patient andbase 14, particularly when transporting patients. Tethered cable 46 (ora direct connect via ports in the base and pod) provides a system foruse when the wireless link between pod 12 and base 14 fails for whateverreason or when precise signal synchronization demands a wiredconnection. Tethered cable 46 also provides the added advantage in thatthe user cannot lose cable 46 because it is tethered to base 14.Wireless links can impose a delay in communication between a pod andbase 14 longer than may be experienced with a cable. When communicationsbetween base 14 and a pod require a faster response time (such asapplication of synchronous cardioversion or pacing where informationfrom a pod must be transmitted to base 14), the user is advised of theneed to plug cable 46 into the pod. The user is provided a userinterface message to inform them of the need to attach cable 46 or todock pod on base and establish a direct wired connection.

With reference again to FIG. 4, system controller module 66 controlsinteraction of all the pod's modules through data bus 64 and interactionwith base 14 through a wired connection, such as tethered cable 46 orwireless (e.g., IrDA, RF, etc.) communication link 72 which would betransmitted by transceiver 32. System control module 66 may also includean interconnect module to assist with wire and wireless communicationsover link 72. Patient parameter module 68 monitors functions such asinvasive blood pressure, patient's temperature, and inputs from the podleads. Module 68 further collects inputs from EtCO₂ module 74, NIBPmodule 76, and SpO₂ module 78 through OEM module 80. Patient parametermodule 68 takes all of these inputs and processes them for display andcan route only a limited number of inputs to small LCD display module 82through operator interface module 70. Operator Interface module 70allows the operator to primarily interact with pod 12; however, it iscontemplated that operator could use the module 70 to interact with base14 as well.

With reference to FIG. 5, a schematic view of a defibrillator/monitor inan embodiment of the present teachings is shown. Base 14 is powered by aremovable/rechargeable battery 84, which provides power to power module86. Alternatively, base 14 could be powered by AC power supply 88 or DCpower supply 93. Power module 86 processes the incoming power intoappropriate powered levels for each of the internal components. Powermodule 86 also routes the base's power supply through main power anddata bus 90 to interconnect module 92, system controller module 94,therapy module 96, and operator interface module 98. Interconnect module92 is utilized to detect how pod 12 is connected to base 14 (wirelessly,docked, or tethered cable). Although interconnect module 92 is shownseparate from system control module 94, it is contemplated that thesecould both be part of the system control module 92. When pod 12 isdocked or tethered to base 14, interconnect module 92 can route thepower provided from power module 86 to the pod 12 as discussed in PCTapplication titled “AN EXTERNAL DEFIBRILLATOR WITH POWER AND BATTERYSHARING CAPABILITIES WITH A POD,” International Application No.PCT/US2004/042376, Attorney Docket Number 539.6000.11 filed Dec. 17,2004. Additionally interconnect module 92, in conjunction with systemcontroller 94, stores all of the information about the associations thathave been established between the base 12 and pod 14. Similar to systemcontroller module 66 (in FIG. 4), system controller module 94 controlsall interaction of all of the base's modules through data bus 90 andinteraction with pod 12 through wired or wireless connectioncommunication link 72 or through data bus 90 if pod 12 is connected tobase 14. System controller module 94 and interconnect module 92 have theability to encrypt data communicated over the wireless links to meetHIPAA requirements for the protection of patient data. Therapy module 96synchronizes shocks and pacing pulses to the patient's intrinsic rhythmfrom data acquired from pod 12. Module 96 administers shocks fromvoltages via the defibrillation cap 100 and, in turn, administers pacingpulses to a patient. Operator interface module 98 allows the operator toprimarily interact with base 14; however, it is contemplated that theoperator could use the module 98 to interact with pod 12 as well. Forexample, patient demographic data (e.g., age, sex, height, weight) couldbe entered at the base 14, and communicated to the pod 12 for use ininterpretive algorithms performed in system controller 66 within pod 12.LCD module 102 allows the operator to view a patient's monitoredparameters. Finally, the operator has the option to print out patientinformation on a printer 104 (e.g., a 100 mm strip chart printer).

With reference to FIG. 6, a diagram of a patient module pod and adefibrillator/monitor base interaction in an embodiment of the presentteachings is shown.

In the present embodiment, the pods are all scalable. For example, asmall pod 110 may provide basic functionality such as ECG acquisitionand capability to administer a corrective therapy and the ability tomeasure SpO₂. A medium sized pod 112 may provide all the basics of smallpod 110 and provide additional functionality such as measuring CO₂ andNIBP. And finally, a large pod 114 may provide the operator all thefunctionality of pod 12. The present embodiment allows for the automatic“association” or “pairing” of base 116 with any of pods 110, 112, and/or114. Therefore, if small 110, medium 112, or large pod 114 were placedwithin slot 118 in base 116, base 116 could automatically detect whatsize of pod it was being associated with and then match the pod withbase 116. In prior solutions, scalability was limited to the base unit.The present embodiment allows for the scalability to be outside of base116 and instead with pods 110, 112, and 114. Automatic associationprovides the ability for base 116 to identify the capability of pods110, 112, and 114 without any operator input.

With reference to FIG. 7, a block diagram of a patient module pod and adefibrillator/monitor base interaction in an embodiment of the presentteachings is shown. The concept of an automatic association can beextended to AC power supply 120 and DC power supply 122, where base 116could communicate battery type and status to the power supply providingpower to the base 116 to control the transfer of power for deviceoperation and battery charging. If base 116 is able to automaticallypair with a power supply and adapt to the power supply's behavior, thereis a reduced need for a docking station 117 to provide power or torecharge batteries 16 and 50. Such behavior adaptation could includedetermining automatically how fast the battery could charge and justexactly what type of circuitry could be used for charging depending onwhether AC power source 120 or DC power source 122 was being used. It iscontemplated base 116 could, similar to pods 110, 112, and 114, have asimilar scalability in that smaller base stations may have a lowercapacity. Furthermore, it is contemplated base 116 could be connected toa personal computer 124 where PC configuration files contain thehardware and software compatibility between the base and the pod. Thesefiles could be stored on PC software and when needed could be downloadedto base 116. Therefore, this could limit the amount of informationneeded on base 116 with respect to all the possible combinationsregarding compatibility between the base stations and the pods. It iscontemplated this automatic association of power supplies orrechargeable batteries could be extended to pods 110, 112, and 114,which could make pods 110, 112, and 114 stand alone devices.

With reference to FIG. 8, a block level diagram of an association systemfor a patient module pod and a defibrillator/monitor base in anembodiment of the present teachings is shown. The present embodimentfacilitates the association of pods 132 and 136 with bases 130 and 134respectively and pre-establishing the authorized combination of thedevices. It is helpful the operator have minimal or no input with theassociation of the pods with the bases.

In some embodiments, the association is made by use of a directconnection either via docking and connection with connector 115 orconnector 115 could be tethered to the base for removal from the baseand connection to a remote pod as discussed above. Therefore, the firsttime the units are powered up, the devices automatically begin theassociation process. This can be referred to as dynamic association.Each pod 132, 136 stores a preset unique identifier. The identifier maybe stored in the system control module 66 (FIG. 4) of pod 132. Once pod132 was placed within port 131, base 130 could interrogate pod 132requesting identification to determine its unique identifier storedwithin pod 132. Pod 132 would electrically transfer its uniqueidentifier to base 130. Base 130 can store the unique identifier forthis “selected” pod 132 in the systems control module 94 (FIG. 5) ofbase 130. Accordingly, if the pod 132 is then separated from base 130,wireless communication may occur between these associated or paireddevices over respective communication links 72 (FIGS. 4 and 5).

As noted above, the wireless communication over link 72 may be via awireless BlueTooth module, or using other communication protocols, suchas WiFi (802.11), Wireless WAN (CDMA, GSM, GPRS, UTMS, etc.). Forinstance, assuming the communication occurs via WiFi, pod 132 will beginto transmit a beacon on a preselected channel once it is unplugged frombase 130. Base 130 will then search for its associated pod. Under common802.11 protocol, the base may start by searching a default frequencychannel in the channels commonly available, then base 130 would scanover a sequence of channels and look for valid 802.11 devices (e.g.,pods) transmitting a beacon signal.

Once the base 130 finds a valid 802.11 device (e.g., a pod transmittinga beacon signal), it will check whether this is the associated pod byquerying the pod's identifier. If the base has found its associated pod,the devices may begin wireless communication as is known under thisprotocol. If the channel used for the initial communication is crowded(e.g., noisy or other devices broadcasting on the same channel),provisions are in place in wireless technologies, such as 802.11 andbluetooth, to automatically conduct channel hopping to find a clearerchannel.

Association can also accomplished via wireless means. For instance, withpod 132 and base 130 separated, an operator could manually initiatetheir association. In this scenario, an operator would input a commandor press a key on user interface module 98 (FIG. 5) of base 130 and onuser interface module 70 (FIG. 4) on pod 132 that initiate theassociation. Both base 130 and pod 132 would then transmit a beaconsignal on preselected frequencies that includes a known tag or flag thatconvey to each other that these are the base and pod to be associated.Base 130 could scan for the pod transmitting this tag following aprocess described above under the standard communication protocols. Oncethe base found a pod transmitting a beacon signal, the base would“listen” to the beacon signal to see whether the pod is transmitting theknown flag indicating that it is the pod to be associated. If so, thenthe base 130 would query this pod for its unique identifier. Instead oftransmitting this identifier electrically, as a docked pod would, thisremote pod transmits its identifier wirelessly to base 130. The pod andbase would then be associated and could begin communication as describedabove.

In addition to manual wireless association, association can also beautomatically accomplished with the 132 and base 130 through a wirelesscommunication of pre-established authentication and authorizationinformation stored within the system controller module 94 andinterconnect module 92 within the base 130.

Dynamic association is especially helpful if a pod were to fail and theoperator desired to put another pod in its place. For example, if pod132 were to fail, then pod 136 could be docked in slot 131 and base 130could dynamically pair new pod 136 with base 130. To verify theassociation was successful, the operator can press a button on base 130or pod 136, which could initiate an audible confirmation and/or a visualLED on the respective pod or base.

With reference to FIG. 11, a flow diagram of association between a podand a base in an embodiment of the present teachings is shown. At state200, initial communication is made between a pod and base 14. This canoccur during docking of the pod with base 14, connecting cable 46 withthe pod, or wireless communications between base 14 and the pod. Base 14interrogates the pod requesting pod identification. Upon receiving podidentification from the pod, the base then determines whether this isthe last pod to which it was associated. If the pod is the same pod towhich base 14 was associated and indication is given to the operatorthat the pod is currently associated with base 14 at state 202. Theoperator can associate a name with each pod unique identifier to aid inhuman understanding. The operator indication can be an audible alarm, avisual indicator, a message on display 102, or a digitized voice withoutdeparting from the present teachings. Once association is determinedbase 14 and the pod resume operation together at state 204.

If base 14 determines it is not currently associated with the pod orthat it has not been associated with any pod, base 14 determines whetherthe pod is either docked with base 14 or connected via cable 46 with thepod at state 206 by interrogating the pod 12 over the wired portion 46of communication link 72. If the pod is not docked or connected withbase 14, base 14 instructs the user to either dock the pod with base 14or connect the pod via cable 46 at state 208. The operator instructionremains until it is determined at state 206 that the pod has been dockedor connected. Once this occurs, base 14 interrogates the pod over thewired portion 46 of the communication link 72, requesting the pod'sunique identifier at state 210. Base 14 then waits for a response fromthe pod at state 212. If the pod does not respond or a predeterminedperiod of time passes, the operator is once again instructed to dock thepod or connect it via cable 46 at state 208. Once base 14 identifies thepod, the pod identification information is compared against informationstored in the system controller 94 of the base 14 indicating if base 14is associated with pod 12. Once the association is identified at state214 all the capabilities of the pod 12 are communicated from pod 12 tobase 14 so base 14 can interact with the pod utilizing all the pod'scapabilities. It is fully contemplated pod identification could beaccomplished in other fashions such as having a look-up table stored inbase 14, downloading the information from a personal computer, orcommunicating with a network without departing from the spirit of thepresent teachings. At state 216, base 14 transfers its identificationinformation to the pod so the pod can identify and store in systemcontroller 66 memory which base 14 it is currently associated with. Base14 then initiates a test with the pod to confirm that base 14 and thepod 12 are properly associated at state 218.

Proper pod and base association is a helpful aspect in accordance withsome embodiments of the system. With further reference to FIG. 12, anembodiment allows for immediate identification of which patient podshould be displayed when a plurality of pods and bases are in closeproximity. It can be contemplated that confusion can occur at a basewhen multiple pods are available for communication. Each pod responds tothe base with a unique identifier over the communication link 72. Thecommunication link 72 uses the unique identifier to ensure communicationwith the correct pod. The unique identifier is preset in a wirelesscommunication module or portion of the pod's system control module 66.The operator can associate a name with each pod unique identifier thatwill be displayed on the base display 102 to inform the operator of theassociation with such pod. The unique identifier facilitates theestablishment of the specific communication links to avoid crosstalk.

In certain embodiments, base 130 could sense the proximity of anotherpod 132 within its range and alert the operator of the other pod'spresence at state 300. Each pod routinely transmitting an identifyingwireless signal could accomplish the proximity sensing. However, othermethods of proximity sensing could be used such as each pod routinelytransmitting an audible sound without departing from the spirit of thepresent teachings. If no other pod is sensed within the base'sproximity, then base 130 resumes normal operation at state 302. Ifanother pod is detected within the base's proximity, then the operatormay then be directed to interact with the base or pod, for example, bymanually pressing a locator button 121 (FIG. 7) thereon at state 304.This action could cause the pod or base to respond in some way (e.g.visual or audible alert) to let the operator know which is the propermate to the base or pod. The operator could also attach serial cable 46to pod 132 or momentarily plug patient pod 132 into slot 131 of base130. Whether by a cable or by docking pod 132, pod 132 and base 130identify each other, and communicate only with each other until anothersuch mating of a different pod with base 130 occurs. In this way, anoperator could determine whether or not the pod association hadaccidentally been switched. This could eliminate the possibility ofinappropriate diagnosis or delivery of therapy.

The locator button could also be used to locate an associated pod.Although the pod is generally associated to the one base, events mayoccur in which there are multiple patients, and in turn, multiple basesand corresponding pods. During such events, the multiple pods may beinadvertently transposed, possibly due to identical equipment being usedin regard to the multiple bases and pods. As discussed above, base 130and pod 132 could provide circuitry or programming to sense the presenceof another pod within its range at state 300 (or a specified distancefor example five feet) and instruct the operator to manually press abutton on the module at state 304. Pod 132, to which base 130 isassociated, could respond, thereby eliminating confusion and possiblyavoiding inappropriate diagnosis or delivery of therapy.

With reference to FIG. 13, a flow diagram of a pod location function inan embodiment of the present teachings is shown. It is contemplated thatafter having been taken off the base, the pod may be forgotten or lost.At state 400, if base 130 and pod 132 are not physically connected, base130 periodically determines how long it has been since it had wirelesscommunications with pod 132. If the amount of wireless inactivity isbelow a predetermined amount of time, then base 130 resumes normaloperation at state 402. However, after a certain amount of wirelessinactivity time between pod 132 and base 130, an alarm could go off atbase 130 and/or pod 132 at state 404. If base 130 is turned off and pod132 is remotely located, after a certain amount of inactivity time, suchas several minutes (state 406), pod 132 could enter “sleep mode” (i.e.,pod is on, but using a reduced amount of power to maintain itsactivation) to preserve power at state 408. When base 130 was turnedback on, wireless communications could be used to detect pod 132, awakenpod 132, and initiate an audible alarm on pod 132 to indicate where pod132 is located. Alternatively, the operator could initiate the podfinder action on the screen at base 130.

In certain embodiments, base 130 could act as a hub, which could talk tomultiple pods. An operator interface is placed on the display screen ofbase 130 and allows the operator to select which pod to listen to. Theoperator could test each pod by sending a signal to a particular pod todetermine which pod they are trying to connect to. The operator couldpress a button and the pod could blink or enunciate to the operator insome manner that it is linked to the base. Provided the pod and base areassociated, a signal could instead be initiated by the pod to confirmthat the pod is, in fact, talking to the base.

Configuring the base 130 as a hub could be especially helpful insituations where there was a large response team to several patients.Base 130 could allow the operator to select which pod they want toreceive patient information from as noted above. Furthermore, base 130could be able to make an automatic selection on which pod to show on thescreen based upon a patient parameter that indicated the patient was insome sort of immediate danger. This could be performed by the systemcontroller 94 routing all data into similar patient analysis algorithms,which could look for abnormalities in the signals. Under this hubconfiguration, base 130 could collect information from the multiple podsbut could only display information from the one selected pod.

It may be helpful to monitor the wireless connection quality between thebase and the pod over their lifetimes. Monitoring this connection couldbe helpful because each parameter measured by the pod 132 requires acertain amount of bandwidth to be wirelessly transmitted back to thebase 130. If the signal quality from the pod 132 degrades to a certainlevel due to connection quality, then a warning could be issued to theoperator indicating they may need to somehow direct connect the pod 132to the base 130 either via a cable or dock pod 132 within base 130.Furthermore, the operator can have the bandwidth scheme automaticallystep down by requesting fewer parameters from the pod 132.Alternatively, the base and pod could automatically cease or postponecommunication of non-critical information when the communications linkdegrades. For instance, the system controller 66 within pod 132 and thesystem control module 94 (including the Interconnect module 92) withinbase 130 could detect when the signal quality degrades (e.g., certainnumber of errors detected) to a threshold level and could step downcommunications to a level that merely includes patient vital signs.

One skilled in the art will appreciate that the present teachings can bepracticed with embodiments other than those disclosed. The disclosedembodiments are presented for purposes of illustration and notlimitation, and the present teachings are limited only by the claimsthat follow.

1. A modular external defibrillator system for treating a patient, comprising: a base containing a display and an external defibrillator module configured to deliver a defibrillation shock to the patient; a first pod operable when separated from the base, the first pod having a first patient parameter module and connectable to the patient to collect first patient data related to at least a first patient vital sign, the first pod capable of wirelessly transmitting the first patient data to the base; and a second pod operable when separated from the base, the second pod having a second patient parameter module and connectable to the patient to collect second patient data related to at least a second patient vital sign independent from the first vital sign, the second pod capable of wirelessly transmitting the second patient data to the base, in which, when one of the first or the second patient data is transmitted to the base, the base is configured to display an aspect of the transmitted one of the first or the second patient data.
 2. The external defibrillator system of claim 1, in which the external defibrillator module is configured to deliver the defibrillation shock based on the one of the first or the second patient data transmitted to the base.
 3. The external defibrillator system of claim 1, in which the first pod contains an interpretive algorithm to analyze a patient condition based on the first patient data.
 4. The external defibrillator system of claim 1, in which, while the base is receiving the first patient data, the base is configured to sense a nearby presence of the second pod, and provide an alert in response to sensing the second pod.
 5. The external defibrillator system of claim 1, in which the one of the first or the second patient data that is transmitted to the base is encrypted.
 6. The external defibrillator system of claim 1, in which the base is configured to control which of the first or the second pods is selected over the other.
 7. The external defibrillator system of claim 1, in which the selection of the selected pod is based on which of the first or the second pods is electrically directly connected to the base.
 8. The external defibrillator system of claim 1, in which a unique pod identifier is transmitted from the selected pod to the base.
 9. The external defibrillator system of claim 1, in which the selected pod is configured to provide an indication when prompted by the base to confirm that the selected pod has been selected over the other pod.
 10. The external defibrillator system of claim 1, in which, when the base and the selected pod are communicating wirelessly over a link, if the link degrades, one of the base or the selected pod is configured to provide an alert.
 11. The external defibrillator system of claim 1, in which, when the base and the selected pod are communicating wirelessly over a link, if the link degrades, less patient data is carried to the base.
 12. The external defibrillator system of claim 1, in which, when the base and the selected pod are communicating wirelessly over a link, if the link is lost, the system is configured to output an alarm.
 13. The external defibrillator system of claim 12, in which if the link is not reestablished within a preset time period after the alarm is output, the selected pod configured to enter a sleep mode.
 14. A method for a modular external defibrillator system for treating a patient, the system including: a base containing a display and an external defibrillator module configured to deliver a defibrillation shock to the patient, a first pod operable when separated from the base, the first pod having a first patient parameter module and connectable to the patient to collect first patient data related to at least a first patient vital sign, the first pod capable of wirelessly transmitting the first patient data to the base, and a second pod operable when separated from the base, the second pod having a patient parameter module and connectable to the patient to collect second patient data related to at least a second patient vital sign independent from the first vital sign, the second pod capable of wirelessly transmitting the second patient data to the base, the method comprising: selecting one of the first or the second pods over the other; establishing a communications link between the base and the selected pod, in which the one of the first or the second patient data collected by the selected pods is transmitted wirelessly to the base; and displaying at the display an aspect of the transmitted one of the first or the second patient data.
 15. The method of claim 14, further comprising: delivering a defibrillation shock based on the one of the first or the second patient data transmitted to the base.
 16. The method of claim 14, further comprising: analyzing a patient condition based on an interpretive algorithm in the selected pod and the patient data collected by the selected pod.
 17. The method of claim 14, further comprising: while the base has the communications link established with the selected pod, sensing a nearby presence of the second pod, and providing an alert in response to sensing the second pod.
 18. The method of claim 14, in which the one of the first or the second patient data that is transmitted to the base is encrypted.
 19. The method of claim 14, in which the selection is made by electrically directly connecting the one of the first or the second pods to the base.
 20. The method of claim 14, in which a unique pod identifier is carried from the selected pod to the base.
 21. The method of claim 14, in which the selected pod provides an indication when prompted by the base to confirm that the selected pod has been selected over the other pod.
 22. The method of claim 14, in which if the link degrades, one of the base and the selected pod provides an alert.
 23. The method of claim 14, in which if the link degrades, less patient data is carried to the base.
 24. The method of claim 14, in which if the link is lost, an alarm is output.
 25. The method of claim 24, in which if the link is not reestablished within a preset time period after the alarm is output, the selected pod enters a sleep mode. 